Configuration of field devices with a mobile device

ABSTRACT

A method for configuring a target field device in an industrial plant by way of at least one mobile device including receiving configuration data characterizing the behavior of a source field device in the industrial plant from the source field device through the mobile device by way of a radio interface of the mobile device, which is also supported by the source field device, receiving at least one identification feature characterizing a target field device and/or function of the target field device in the industrial plant by a mobile device by way of a radio interface of the mobile device, which is also supported by the target field device checking by way of the mobile device, using the identification feature, whether the configuration data are suitable and/or intended for the configuration of the target field device, and in response to the configuration data being suitable and/or provided for the configuration of the target field device, transmitting at least a subset of the configuration data from the mobile device to the target field device by way of a radio interface of the mobile device which is also supported by the target field device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of the filing date of German PatentApplication No. 10 2019 218 811.7 filed on 3 Dec. 2019, the entirecontent of which is incorporated herein by reference.

FIELD

The disclosure relates to the configuration of field devices used formonitoring, visualisation and control of production processes inindustrial plants.

TECHNICAL BACKGROUND

For monitoring, visualisation and control of industrial productionprocesses, field devices are often used which record physical measuredvariables of the process or intervene in the process to control it.

Field devices are often designed to be universally applicable in avariety of situations and may be configured with a large number ofsetting parameters for their specific application. For this purpose a PCor laptop is connected to a suitable interface of the field device.Increasingly, settings are also made on the field device via wirelessinterfaces using operating devices such as smartphones and tablets. Mostfield devices also have a function with which the complete configurationdata can be downloaded as a backup file and restored later.

Frequently, use is also made of the possibility of changing settingsusing local controls on the field device itself. The backup file mustthen be updated regularly so that a restore will reset the field deviceto its last working state.

A typical industrial plant contains a large number of different fielddevices. These field devices are typically connected to narrow-bandinterfaces at their place of use in an industrial plant, such as currentinterfaces on which analogue information is coded in the form ofcurrents between 4 and 20 mA. A direct connection of the field devicesto a LAN of the industrial plant is usually not planned or not feasibleas industrial requirements with regard to two-wire field devices,explosion protection (especially by intrinsic safety), security, memorysize, speed etc. are not yet sufficiently defined/standardised for fielddevices in industrial plants.

For applications where the field devices can be connected to a centralserver, DE 10 2017 104 912 A1 provides a configuration procedure.

SUMMARY

The present disclosure relates to a method for configuring a targetfield device in an industrial plant by means of at least one mobiledevice. The mobile device may in particular be, for example, asmartphone, a Smartwatch, a tablet or a portable computer with awireless communication interface/radio interface. The field devices inthe industrial installation may include, for example, sensors for level,limit level, pressure, temperature or flow in a container or in a pipe.However, the field devices can also include, for example, valves,positioners, signal conditioning instruments as well as control deviceswhich act on other field devices.

According to an embodiment, configuration data, which characterise thebehaviour of a source field device in the industrial plant andspecifically define the application used, are received from the sourcefield device by the mobile device via a radio interface of the mobiledevice, which is also supported by the source field device. For thispurpose, the source field device can, for example, be selected on themobile device from a list of available field devices which are withinradio range of the field device and can be prompted to send or uploadthe configuration data by a control command transmitted via the radiointerface. However, this is not absolutely necessary. If sufficientbandwidth is available for radio transmission, a field device can also,for example, regularly send its current configuration data on its owninitiative.

Furthermore, at least one identification feature characterising a targetfield device and/or its function in the industrial plant is received bya mobile device. For this purpose, a radio interface of the mobiledevice is used which is also supported by the target field device. Inparticular, the mobile device may be the same one that previouslyreceived the configuration data from the source field device. However,this is not absolutely necessary. For example, a first mobile device mayreceive configuration data from a source field device in a first area orat a first location of the industrial plant and pass it on to a secondmobile device which communicates with the target field device in asecond area or at a second location of the industrial plant. The dataexchange between the first mobile device and the second mobile devicemay then take place, for example, via a cloud, or via direct fileexchange between the first mobile device and the second mobile device,for example, by means of XML files. The mobile device may also move theconfiguration data from a source field device in a radio area A over aphysical path in a radio area B and pass on the data to the field devicethere.

The identification feature may, for example, be a fixed serial numberassigned to the field device, which cannot be changed by the operator ofthe industrial plant. However, the identification feature may also be,for example, a measuring point name or measuring point marking oranother designation which is only unique within the respectiveindustrial installation and is assigned by the operator of theindustrial installation.

In particular, the identifier can be received by the target field deviceusing, for example, a radio interface of the mobile device. This radiointerface can be the same as the one used to receive the configurationdata. However, this is not absolutely necessary. For example, in anindustrial plant, there may be field devices performing the samefunction in relation to the industrial process, in a first version witha radio interface of a first type (approximately 2.4 GHz WLAN) and in asecond version with a radio interface of a second type (approximately 5GHz WLAN or Bluetooth). Field devices have a long service life of up todecades. It is therefore conceivable that a manufacturer of fielddevices, if a new type of radio interface is available, will launch anupdated field device on the market which will behave in the same way asthe previous one with the only difference that it can also be addressedvia the new radio interface. In the meantime/for example LTE-NB1(NB-IoT) or also LoRa WAN can be mentioned here.

For example, field devices may periodically send a beacon signal (forlocalisation purposes) with the identifier. The mobile device canreceive these beacon signals from all field devices within radio range.By an operator of the mobile device or, for example, by comparison withan identification feature of a target field device already stored in themobile device, the mobile device is informed which target field deviceis to be configured.

A field device may also send different beacon signals, for example,depending on whether it has already been configured with configurationdata or not. If the field device has already been configured, it can bespecially configured as a source field device with a correspondingbeacon signal. If, on the other hand, the field device has not yet beenconfigured, it can make itself available as the target field device bymeans of an appropriate beacon signal. In this way, for example,operating errors resulting from swapping the source field device and thedestination field device can be avoided. Such an exchange could resultin the existing configuration of the source field device beingoverwritten by an empty or default configuration of the destinationfield device that has not yet been configured.

In particular, if the mobile device already knows the identificationfeature of the target field device, it is possible to address the targetfield device directly via the radio interface using this identificationfeature. It is not necessary that the target field device then transmitsthis identification feature to the mobile device again via radio; it issufficient to confirm that the field device feels addressed when itsidentification feature is mentioned.

The identification feature of the target field device may have been madeknown to the mobile device in advance, for example during work planning.For example, a technician with the task of configuring three newlyinstalled target field devices can have the identification features ofthese target field devices loaded onto his mobile device immediately.

Using the identifier, it is checked whether the configuration data issuitable and/or intended for the configuration of the target fielddevice. In response to the fact that the configuration data is suitableand/or intended for the configuration of the target field device, atleast a subset of the configuration data is sent from the mobile deviceto the target field device via a radio interface of the mobile device.This is done using a radio interface of the mobile device that is alsosupported by the target field device. Suitable and/or intended generallyapplies to devices with the same physical measuring principle (e.g.source field device is a radar level sensor and target field device isalso a radar level sensor). Not suitable and/or intended would betypical for different physical measuring principles (e.g. source fielddevice is a radar level sensor and target field device is also atemperature transmitter).

It was recognised that in many industrial plants many instances ofcertain field devices perform very similar functions. For example, ifthe industrial plant contains a tank farm consisting of a large numberof comparable tanks, and each of these tanks is equipped with a levelmeasuring device of the same type, then these field devices can beconfigured in essentially the same or identical way. A machine copy ofthe configuration data from one source field device to several targetfield devices is then not only faster than a manual configuration ofeach individual field device, but also less prone to errors. Ifnecessary, individual parameters such as the measuring point name ormeasuring point identification can be adjusted manually and individuallyat a later date.

It has also been recognised that transferring from a source field devicethat is already configured to a target field device is less error-proneand much more direct, faster and possibly safer than, for example,retrieving the configuration data for the target field device from acentral server. Even if it is planned that the configuration data storedfor a field device on the central server is identical to theconfiguration data actually effective in the field device, the realitysometimes looks different. For example, the possibility of configuringfield devices via a central server, usually as an “add-on”, appearsalongside the possibility of also making settings via operating elementsattached to the device itself. This option is used, for example, iffaults occur during the operation of the industrial plant and quickaction is required to ensure that the production process does not cometo a standstill. In such situations, it is possible that the user mayforget to enter the changed configuration data on the server.

It may be advantageous to check especially with the mobile devicewhether the configuration data are suitable and/or intended for theconfiguration of the field device. This is a functionality that may notbe provided by every field device. By shifting this task to the mobiledevice, the procedure can therefore be carried out with very little orno modification to the field devices themselves. It is therefore notnecessary to upgrade the field devices to a “central point”. Older fielddevices in particular can possibly only be retrofitted with newfunctions to a limited extent or not at all due to limited hardwareresources, so that only the already installed functions are availablefor the procedure on the side of these field devices.

Another advantage of using the mobile device may be that it can serve asa physical “bridge” between source field devices and destination fielddevices between which there is no direct radio link. Thus the spatialextent of many industrial plants is greater than the range of usualradio interfaces for licence-free radio applications such as Bluetoothor WLAN. For example, dividing an industrial plant into firecompartments with reinforced concrete walls and steel doors may alsomean that not all field devices can communicate directly with each othervia radio. The mobile device can record configuration data via the radiointerface if it comes within radio range of the source field device. Themobile device can also use the radio interface to return theconfiguration data when it comes within radio range of the target fielddevice.

The procedure may also facilitate the replacement of a field device withan equivalent or better field device, for example in case of a defect.For this purpose, for example, the configuration data of the old fielddevice can be downloaded to the mobile device and then the old fielddevice can be replaced with the new one. The configuration data can thenbe transferred back from the mobile device to the new field device, sothat the new field device then behaves in the same way as the originalfield device. The same applies if only the electronics of a field deviceare replaced with new electronics. The source field device and thetarget field device are identical in this special case.

In a particularly advantageous embodiment, at least one identificationfeature is received from each of several field devices. The reception ofconfiguration data involves requesting a selection of the field devicefrom which configuration data is to be obtained from the several fielddevices as source field device from an operator of the mobile device.If, for example, the operator of the mobile device enters an area of theindustrial plant, a radio device list of the field devices currentlywithin radio range can be presented to him. The operator may then selectthe suitable source field device from this radio device list.

Such, or the same, radio device list can also be used to select thetarget field device. In another advantageous design, at least oneidentification feature is received from several field devices. The checkinvolves requesting from an operator of the mobile device a selection ofthose field devices to which the configuration data are to be sent fromthe several field devices as target field devices.

In another configuration, at least one identification featurecharacterising the source field device and/or its function in theindustrial plant is received by the mobile device. The check whether theconfiguration data are suitable and/or intended for the configuration ofthe field device includes a comparison of this identification featurewith the identification feature of the target field device. For example,the identifier may include a type designation of the field device, whichmay optionally be provided with, for example, a version or revisionnumber. The mobile device can then store, for example, which devicetypes, versions or revisions are upward or downward compatible with eachother. Thus, for example, configuration data of an older field devicethat has a certain functionality can also be used by a newer fielddevice with an extended functionality compared to the older fielddevice. On the other hand, configuration data of the newer field devicecan only be used by the older field device if only those functions areused which are also implemented in the older field device.

Therefore, in response to the fact that a target field device is of thesame type as the source field device or a compatible type, theconfiguration data may be found to be suitable for the configuration ofthat target field device.

According to an embodiment, a subset of the configuration data isadapted to the needs of the target field device. The configuration ofthe destination field device need not therefore be a 1:1 copy of theconfiguration of the source field device. For example, it may not beappropriate for the destination field device to have the same name ornetwork address (in cases of, for example, Profibus networks or HARTmultidrop networks) as the source field device. A tank farm, forexample, can also—consist of tanks of different sizes, and theconfiguration of level measuring devices can then contain informationabout the size of the tank on which they are mounted. The adjustmentdoes not necessarily have to be made on the mobile device, but can alsobe made in a cloud, for example, to which the configuration data hasbeen transferred from the mobile device.

In particular, for example, at least one identification feature of thesource field device contained in the configuration data can be replacedby a new identification feature of the destination field device. Forexample, when transferring to the target field device, you may be askedfor a new measurement point name to be assigned to the target fielddevice.

As explained above, the configuration data of field devices can changeduring operation of the industrial plant, e.g. by direct manual entrywith control elements on the field device itself. Therefore, theconfiguration data transferred to the mobile device may become obsolete.In another particularly advantageous design, the configuration data aretherefore no longer considered suitable for the configuration of targetfield devices after a specified period of time has elapsed from the timethey were received by the source field device. They therefore have an“expiry date”. This can be combined in particular with the fact that forthe specified period of time for which the configuration datatransmitted to the mobile device is to be valid for the configuration offurther field devices, a change to the configuration data of the sourcefield device is blocked. Such a lock can then also apply to the targetfield devices to which this configuration data is transferred. If, forexample, a technician configures a large number of target field devicesin a tank farm from a source field device with a mobile device, thefield devices will not accept any further changes by other operatorsuntil the technician has finished configuring all field devices in thetank farm.

According to an embodiment, the position of at least one source fielddevice, and/or the position of at least one destination field device, inthe industrial installation is determined by comparing at least oneidentifier of this field device with a plan of the industrialinstallation stored on the mobile device. This plan may be in the formof a drawing or a three-dimensional model. This can make it easier for atechnician to find the source field device or the target field deviceand avoid confusion. For example, work orders of the type “today pleaseconfigure the field devices in the left half of the tank farm” are proneto such mix-ups if the hall with the tank farm has several entrances.

Therefore, in another particularly advantageous configuration, themobile device calculates a route from the current position of the mobiledevice to a source field device, and/or to a destination field device,based on the plan of the industrial plant. This route can be offeredoptimised by internal algorithms in the mobile device with regard to atleast one given criterion. For example, the route can be optimised sothat the technician can use the ideal route (shortest route or deviceswith highest priority first), resulting in work optimisation.

The position of the mobile device in the industrial plant can beevaluated in particular, for example, by using the signal strengths withwhich signals from several field devices are received by at least oneradio interface of the mobile device. Satellite-based navigation systemscannot always be received well enough to determine the position with therequired accuracy within industrial installations located in enclosedbuildings.

According to an embodiment, a level meter, level limit meter, densitymeter, flow meter, pressure meter, valve, positioner, signalconditioning instrument or control unit is selected as source fielddevice, and/or as target field device. Especially of these types offield devices, there are often accumulations of many instances inindustrial plants, where a uniform configuration makes sense.

The configuration data may, in particular, include, for example,parameters of at least one function rule, on the basis of which thesource field device, or the target field device, processes values of atleast one physical measured variable that it has recorded. For example,the parameters may comprise interpolation points of a linearizationcurve with which physical measurement data recorded by the field deviceare added to a quantity output by the field device.

In particular, the procedures may be wholly or partlycomputer-implemented. Therefore, the present disclosure also relates toa computer program containing machine-readable instructions which, whenexecuted on one or more computers, cause the computer or computers tocarry out one of the processes described. In this sense, field devicesand embedded systems for technical apparatus which are also capable ofexecuting machine-readable instructions are also considered to becomputers.

Likewise, the present disclosure also relates to a machine-readable datacarrier and/or a download product containing the computer program. Adownload product is a digital product which can be transmitted via adata network, i.e. downloaded by a user of the data network, and whichcan be offered for immediate download in an online shop, for example.

Furthermore, a computer may be equipped with the computer program, themachine-readable data carrier or the download product.

SHORT DESCRIPTION OF THE FIGURES

In the following, the subject is further described, without limiting thesubject of the present disclosure. It is shown:

FIG. 1: Embodiment of the procedure 100;

FIG. 2: Different scenarios for the application of the procedure 100.

DETAILED DESCRIPTION OF EMBODIMENTS

FIG. 1 is a schematic flowchart of an embodiment of method 100. In step101, a level meter, level limit meter, density meter, flow meter orpressure meter can be selected as source field device 2, and/or astarget field device 3.

In step 110, configuration data 5, which characterises the behaviour ofthe source field device 2, is received from the source field device 2 bya mobile device 4 via a radio interface.

In step 120, at least one identifier 3 a characterising the target fielddevice 3 and/or its function in the industrial plant 10 is received by amobile device 4, 4′. This mobile device 4, 4′ may be identical to themobile device 4 that previously received the configuration data 5.However, it may also be, for example, another mobile device 4′ locatedin another area or at another site of the industrial installation 10 andreceiving configuration data 5 by any means. These two alternatives arefurther explained in FIG. 2.

In step 130, the mobile device 4, 4′ is used to check whether theconfiguration data 5 are suitable and/or intended for the configurationof the target field device 3, using the identification feature 3 a. Ifthis is the case (truth value 1), the configuration data 5 is sent tothe target field device 3. In doing so, configuration data 5 can beadapted to the needs of the target field device 3 according to block 135and is therefore designated with the reference character 5′. Inparticular, according to block 135 a, an identification feature 2 a ofthe source field device 2 contained in configuration data 5 can beexchanged for an identification feature 3 a of the destination fielddevice 3 which is to be newly assigned.

According to block 105, identification features 1 a can be received fromseveral field devices 1 in industrial plant 10. This makes it possible,in accordance with block 111, to request an operator of mobile device 4to select one of these field devices 1 as source field device 2. In thesame way, a selection of one of the field devices 1 as target fielddevice 3 can be requested by an operator of the mobile device 4, 4′ inaccordance with block 131.

According to block 112, the mobile device can receive an identificationfeature 2 a characterising the source field device and/or its functionin Industrial Plant 10. This identification feature can then be matchedwith the identification feature 3 a of the target field device 3according to block 132. If this comparison 132 shows that thedestination field device 3 is of the same type as the source fielddevice 2 or of a compatible type (truth value 1), the configuration data5 can be found to be suitable for the configuration of the destinationfield device 3 in accordance with block 133.

According to block 134, configuration data 5 can be considered as nolonger suitable for the configuration of target field devices 3 after aspecified period of time has elapsed from the time it was received bythe source field device 2. Configuration data 5 is therefore obsoleteafter this period of time.

According to block 136, position 2 b of source field device 2, and/orposition 3 b of destination field device 3, can be determined from acomparison of the respective identification feature 2 a, 3 a with a plan11 of industrial installation 10. Then, according to block 137, a route12 can be calculated from the current position 4 b of the mobile device4, 4′ to the source field device 2, and/or to the destination fielddevice 3. This makes it easier to visit the source field device 2 or thedestination field device 3 with the mobile device 4, 4′ in order tocontact it for the purpose of receiving 110 configuration data 5 orsending 140 configuration data 5. The position 4 b of the mobile device4, 4′ can be evaluated according to block 102 in particular from signalstrengths with which signals from several field devices are receivedthrough a radio interface of the mobile device 4, 4′.

FIG. 2 shows an exemplary scenario in an industrial plant 10, which hereis divided into three areas A, B, C. Areas A and B are at the same site,area C is at a different location. Procedure 100 is used in the exampleshown in FIG. 2 to configure a large number of target field devices 3 inall three areas A, B and C, starting from a single source field device 2in area A.

The source field device 2 transmits its identification feature 2 a aswell as its configuration data 5 to the mobile device 4. Within area A,the mobile device 4 can then distribute the configuration data 5directly from its position 4 b. The mobile device 4 receives therespective identification feature 3 a from each target field device 3and in return transmits the configuration data 5 or the version 5′adapted to the respective target field device.

When the mobile device 4 reaches the new position 4 b′ in area B, it canconnect to other target field devices 3 there and distributeconfiguration data 5, 5′ in the same way as it did before in area A.

The configuration data 5, 5′ can also be used in area C at the remotesite. For this purpose, the mobile device 4 can transmit theconfiguration data 5, 5′ to a cloud 13. Another mobile device 4′ atlocation 4 b″ in area C can retrieve the configuration data 5, 5′ fromthe Cloud 13 and distribute them in area C in the same way as if it hadpreviously captured them in area A itself.

LIST OF REFERENCE SIGNS

-   1 Field device-   1 a Identification feature of the field device 1-   2 Source field device as field device 1-   2 a Identification feature of the source field device 2-   2 b Position of the source field device 2-   3 Target field device as field device 1-   3 a Identification feature of the target field device 3-   3 b Position of the target field device 3-   4 mobile unit, movable from area A to area B-   4′ mobile device in area C-   4 b Position of mobile device 4 in area A-   4 b′ Positions of mobile device 4 in area B-   4 b″ Position of mobile device 4′ in area C-   5 Configuration data-   5′ Configuration data adapted to target field device 3-   10 Industrial plant-   11 Plan of the industrial plant 10-   12 Route within the industrial plant 10-   13 Cloud-   100 Method-   101 Selecting source field device 2 and/or destination field device    3-   102 Determining position 4 b from received signal strengths-   105 Receiving many identification features 1 a from field devices 1-   110 Receiving configuration data 5-   111 Requesting a selection of the source field device 2-   112 Receiving the identifier 2 a-   120 Receiving the identifier 3-   130 Check whether configuration data 5 is suitable/intended for    target field device 3-   131 Requesting a selection of the target field device 3-   132 Comparison of identification features 2 a and 3 a-   133 Release of configuration data 5 for compatible devices 2, 3-   134 Expiry of configuration data 5 after a defined period of time-   135 Adjusting the configuration data 5 for target field device 3-   135 a Exchange of identification feature 2 a for feature 3 a-   136 Determining items 2 b, 3 b from comparison with plan 11-   137 Calculating a route 12 within the industrial plant 10-   140 Send configuration data 5, 5′ to target field device 3-   A, B areas of industrial plant 10 on the same site-   C area of industrial plant 10 on remote site

1. A method for configuring a target field device in an industrial plantby way of a mobile device, comprising: receiving configuration datacharacterizing behavior of a source field device in the industrial plantfrom the source field device through the mobile device by way of a radiointerface of the mobile device, which is also supported by the sourcefield device; receiving at least one identification featurecharacterizing a target field device and/or function of the target fielddevice in the industrial plant by the mobile device by way of a radiointerface of the mobile device, which is also supported by the targetfield device; checking by way of the mobile device, using theidentification feature, whether the configuration data are suitableand/or intended for the configuration of the target field device; and inresponse to the configuration data being suitable and/or provided forthe configuration of the target field device, transmitting at least asubset of the configuration data from the mobile device to the targetfield device by way of a radio interface of the mobile device which isalso supported by the target field device.
 2. The method according toclaim 1, wherein at least one identification feature is received from aplurality of field devices in each case, and wherein the receiving ofthe configuration data includes requesting a selection of that fielddevice from which configuration data is to be obtained from theplurality of field devices as source field device from an operator ofthe mobile device.
 3. The method according to claim 1, wherein at leastone identification feature is received from a plurality of field devicesin each case, and wherein the checking includes requesting from anoperator of the mobile device a selection of those field devices towhich the configuration data are to be sent from the plurality of fielddevices as target field devices.
 4. The method according to claim 1,wherein at least one identification feature characterizing the sourcefield device and/or function of the source field device in theindustrial plant is received by the mobile device, and wherein thechecking includes a matching of this identification feature with theidentification feature of the target field device.
 5. The methodaccording to claim 4, wherein in response to the target field devicebeing of a same type as or compatible with the source field device withrespect to matching, the configuration data is found to be suitable forthe configuration of the target field device.
 6. The method according toclaim 1, wherein a subset of the configuration data is adapted to needsof a target field device.
 7. The method according to claim 6, wherein atleast one identification feature of the source field device contained inthe configuration data is replaced by a new identification feature forthe target field device.
 8. The method according to claim 1, wherein theconfiguration data is determined as no longer suitable for configurationof target field devices after a predetermined period of time has elapsedfrom a time at which the configuration was received by the source fielddevice.
 9. The method according to claim 1, wherein a position of atleast one source field device, and/or a position of at least one targetfield device, in the industrial plant is determined from a comparison ofat least one identification feature of the at least one source or targetfield device with a plan of the industrial plant stored on the mobiledevice.
 10. The method according to claim 9, wherein a route (12) from acurrent position of the mobile device to a source field device and/or toa destination field device is calculated by the mobile device on a basisof the plan of the industrial plan, optimized with respect to at leastone predetermined criterion.
 11. The method according to claim 1,wherein a position of the mobile device in the industrial plant isevaluated using signal strengths with which signals from several fielddevices are received by at least one radio interface of the mobiledevice.
 12. The method according to claim 1, wherein a level measuringdevice, limit level measuring device, density measuring device, flowmeasuring device, pressure measuring device, valve, positioner,evaluation device or control device is selected as the source fielddevice and/or as the target field device.
 13. The method according toclaim 1, wherein the configuration data include parameters of at leastone functional rule, on a basis of which the source field device, or thetarget field device, processes values of at least one physical measuredvariable which the source or target field device has recorded.
 14. Anon-transitory computer readable medium having stored thereon a programcontaining machine-readable instructions which, when executed on one ormore computers, cause the computer or computers to perform a method forconfiguring a target field device in an industrial plant by way of amobile device, comprising: receiving configuration data characterizingbehavior of a source field device in the industrial plant from thesource field device through the mobile device by way of a radiointerface of the mobile device, which is also supported by the sourcefield device; receiving at least one identification featurecharacterizing a target field device and/or the function of the targetfield device in the industrial plant by the mobile device by way of aradio interface of the mobile device, which is also supported by thetarget field device; checking by way of the mobile device, using theidentification feature, whether the configuration data are suitableand/or intended for the configuration of the target field device; and inresponse to the configuration data being suitable and/or provided forthe configuration of the target field device, transmitting at least asubset of the configuration data from the mobile device to the targetfield device by way of a radio interface of the mobile device which isalso supported by the target field device.
 15. A device comprising:processing circuitry; and memory storing instructions for configuring atarget field device in an industrial plant by way of a mobile devicethat when executed by the processing circuitry causes the processingcircuitry to be configured to: receive configuration data characterizingbehavior of a source field device in the industrial plant from thesource field device through the mobile device by way of a radiointerface of the mobile device, which is also supported by the sourcefield device, receive at least one identification feature characterizinga target field device and/or the function of the target field device inthe industrial plant by the mobile device by way of a radio interface ofthe mobile device, which is also supported by the target field device,check by way of the mobile device, using the identification feature,whether the configuration data are suitable and/or intended for theconfiguration of the target field device, and in response to theconfiguration data being suitable and/or provided for the configurationof the target field device, transmit at least a subset of theconfiguration data from the mobile device to the target field device byway of a radio interface of the mobile device which is also supported bythe target field device.
 16. The method according to claim 2, wherein atleast one identification feature characterizing the source field deviceand/or the function of the source field device in the industrial plantis received by the mobile device, and wherein the checking includes amatching of this identification feature with the identification featureof the target field device.
 17. The method according to claim 3, whereinat least one identification feature characterizing the source fielddevice and/or the function of the source field device in the industrialplant is received by the mobile device, and wherein the checkingincludes a matching of this identification feature with theidentification feature of the target field device.
 18. The methodaccording to claim 2, wherein a subset of the configuration data isadapted to needs of a target field device.
 19. The method according toclaim 3, wherein a subset of the configuration data is adapted to needsof a target field device.
 20. The method according to claim 4, wherein asubset of the configuration data is adapted to needs of a target fielddevice.